| 翻訳と辞書 |
| Law of conservation of complexity ： ウィキペディア英語版 |
Law of conservation of complexity
The law of conservation of complexity in human–computer interaction states that every application has an inherent amount of complexity that cannot be removed or hidden. Instead, it must be dealt with, either in product development or in user interaction.
This poses the question of who should be exposed to the complexity. For example, should a software developer add complexity to the software code to make the interaction simpler for the user or should the user deal with a complex interface so that the software code can be simple?
==Background==
While working for Xerox PARC in the mid-1980s, Larry Tesler realized that the way users interact with applications was just as important as the application itself.〔 The book ''Designing Interactions'' by Dan Saffer,〔("Designing Interactions" by Dan Saffer at amazon.com )〕 includes an interview with Larry Tesler that describes the law of conservation of complexity. 〔 The interview is popular among user experience and interaction designers.
Larry Tesler argues that, in most cases, an engineer should spend an extra week reducing the complexity of an application versus making millions of users spend an extra minute using the program because of the extra complexity.〔 However, Bruce Tognazzini proposes that people resist reductions to the amount of complexity in their lives.〔(The Complexity Paradox - Bruce Tognazinni )〕 Thus, when an application is simplified, users begin attempting more complex tasks.
抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』
■ウィキペディアで「Law of conservation of complexity」の詳細全文を読む
スポンサード リンク
| 翻訳と辞書 : 翻訳のためのインターネットリソース |
Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.
|
|